Adding Maven cache to CircleCI config #503
Conversation
carlosroman
force-pushed
the
carlosroman/circleci-deps-cache
branch
3 times, most recently
from
844cfcb to
0ee28f8
Compare
carlosroman
force-pushed
the
carlosroman/circleci-deps-cache
branch
from
0ee28f8 to
9a3c843
Compare
| - restore_cache: | ||
| name: Restore Maven cache | ||
| keys: | ||
| # when pom.xml file changes, use increasingly general patterns to restore cache |
There was a problem hiding this comment.
could you explain this a little? The save-cache step uses the maven-cache anchor, which appears to be defined here.
So the value for maven-cache is (for example) maven-cache-master-ab2c3ffef33. What are the other 2 below this then?
There was a problem hiding this comment.
The other two are there incase this is a brand new branch. If the branch is new it will then try and find the latest cache that begins maven-cache-{{ .Branch }}- and if that fails then just grabs the latest version of the cache that maches maven-cache- (i.e. any branch). It then will save the cache after the first run as maven-cache-{{ .Branch }}-{{ checksum "pom.xml" }}-lint as that is what the maven-cache anchor value is.
There was a problem hiding this comment.
ooooh, thanks, that is helpful. So the anchor value for maven-cache is always the first (most specific) key. The cache-loading is circle-ci functionality that will pick the best key, but when it goes to save the key, it will save with the most specific key.
Noticed some tests failing due to not being able to pull dependencies down. Adding a cache in hope that it will stop that issue coming up again.
Caching doesn't work for the misbehaving JMX server as that is built in Docker and currently no way to share dependencies with the build process in Container Tests.